Configure Network Load Balancer

Prerequisites

  • Create or update Security Group polices of GigaVUE Cloud Suite components. Refer to Security Group Security Group topic for detailed information.
  • Create or update routes in various VPCs across participating mirrored AWS accounts so that all mirrored account VPCs can connect to the target account VPC where the AWS Network Load Balancer is deployed. Refer to Amazon VPC for more information.

    Note:  The target account VPC is considered as the centralized VPC by GigaVUE-FM and the connections towards all other mirrored account VPCs either through 1 : 1 VPC peering or via 1 : M transit gateway (that connects all participating VPCs across mirrored AWS accounts). VPC peering has no bandwidth limitation and no additional cost within the same region (recommended). Transit gateway costs more and it also has a limitation of 50 Gbps burst per VPC.

  • Create or update existing IAM role for GigaVUE-FM in the centralized VPC. Additionally trust relationship needs to be created between the mirrored and the target account for GigaVUE-FM to execute the above permissions at the IAM role level. Refer to AMI and Permissions section for detailed information.
  • User and Password provided in the registration data must be configured in the User Management page for deploying GigaVUE V Series Node using Third Party Orchestration. Refer to Configure Role-Based Access for Third Party Orchestration for more detailed information.

Points to Note:

When configuring Network Load Balancer, the GigaVUE V Series Nodes must be deployed using Third Party Orchestration.

Perform the following steps to configure an external load balancer in AWS:

  1. In the Target Groups page, click Create target group and the Create target group wizard appears. Enter or select the following values and create the target group.
    1. Select IP addresses as the target type.
    2. Enter a name for the target group.
    3. Select the UDP as the Protocol and 4789 as the port number.
    4. Select the VPC of your target group where the targets are registered.
    5. Select TCP as the Health check protocol in port number 8889 with 10 seconds health check interval.

    Note:  For detailed instructions, refer to Create a target group for your Network Load Balancer topic in the AWS Elastic Load Balancing document.

  2. Navigate to the Load Balancer page and click Create Load Balancer the Create elastic load balancer wizard appears. Enter or select the following values and create the load balancer.
    1. Select Network Load Balancer as the load balancer type and click Create.
    2. Enter a name for the Network Load Balancer.
    3. Select Internal load balancer as the Scheme.
    4. Select the VPC for your targets (GigaVUE V Series Nodes).
    5. Select the regions/zones and the corresponding subnets.
    6. Select UDP as the Listener Protocol with Port number 4789.

    Note:  For detailed instructions, refer to Create a Network Load Balancer topic in the AWS Elastic Load Balancing document.

  3. Navigate to the Launch Templates page and click Create launch template the Create launch template wizard appears. Enter or select the following values and create the launch template.
    1. Enter a name for the launch template.
    2. Select the AMI of the GigaVUE V Series node.
    3. Select t3a.xlarge as the instance type.
    4. Select a Key pair for the instance.
    5. Select VPC as the Networking platform and don't specify the security group.
    6. Add 2 Network Interfaces for the GigaVUE V Series Node with device index as 0 and 1 (mgmt and data interface respectively) and for the interfaces, select the appropriate security group.
    7. In the Advanced details section, enter the User data as text in the following format and deploy the instance. The GigaVUE V Series Nodes uses this user data to generate config file (/etc/gigamon-cloud.conf) used to register with GigaVUE-FM using Third Party Orchestration.
      Copy
      #cloud-config
       write_files:
       - path: /etc/gigamon-cloud.conf
         owner: root:root
         permissions: '0644'
         content: |
           Registration:
              groupName: <Monitoring Domain Name>
              subGroupName: <VPC Name>
              user: <Username>
              password: <Password>
              remoteIP: <IP address of the GigaVUE-FM>
              remotePort: 443

    Note:  For detailed instructions, refer to Creating a launch template for an Auto Scaling group topic in the AWS EC2 Auto Scaling document.

  4. Navigate to the Auto Scaling groups page, and click Create an Auto Scaling group the Create Auto Scaling group wizard appears. Enter or select the following values and create the Auto Scaling group.
    1. Enter a name for the Auto Scaling group.
    2. Select an existing launch template.
    3. Select the VPC and subnet.
    4. In the Group size section, enter the Desired capacity as 0. The Desired capacity value must be less that the Maximum Capacity value.

      Note:  Once the monitoring Domain and connection is configured, edit this value to the number of GigaVUE V Series Node that needs to be deployed in this Monitoring Domain.

    5. In the Scaling policies section, select Target tracking scaling policy and choose Average network in (bytes) for the Metric type with 1000000000 (bytes) as target value and 300 seconds warm up value.
    6. (optional) Add Tags to the instances.

    Note:  For detailed instructions, refer to Creating an Auto Scaling group using a launch template topic in the AWS EC2 Auto Scaling document.

In the Instances page, you can view the GigaVUE V Series Node instance deployed by the load balancer.